- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3.6k
branch-3.1: [feature](maxcompute)support maxcompte catalog read project-schema-table. #57012 #57286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    Conversation
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
    …ble. (#57012) ### What problem does this PR solve? Problem Summary: In the previous MaxCompute architecture, and its mapping in Doris, the hierarchy was: `project / database -> table / table`. When creating a catalog, users needed to specify the property `mc.default.project`, which indicated the default project to access. In this structure, executing `SHOW DATABASES` would list other projects. After MaxCompute introduced the concept of schemas, the hierarchy changed to: `project / catalog -> schema / database -> table / table`. Here, the project is at a higher level, and `SHOW DATABASES` should now list all schemas under the current project. As a result, users need to create a separate catalog for each project, specifying a different `mc.default.project` property. doc: https://help.aliyun.com/zh/maxcompute/user-guide/schema-related-operations?spm=a2c4g.11186623.help-menu-search-27797.d_0#9d8326491bagj To maintain compatibility with the old version, a catalog property `mc.project.schema.table` is introduced: - When the property is true, the new architecture is used. - When the property is false, the old architecture is used.
| Thank you for your contribution to Apache Doris. Please clearly describe your PR: 
 | 
| run buildall | 
| TPC-H: Total hot run time: 32417 ms | 
| TPC-DS: Total hot run time: 193004 ms | 
| ClickBench: Total hot run time: 29.43 s | 
| FE UT Coverage ReportIncrement line coverage  | 
              
                    morrySnow
  
              
              approved these changes
              
                  
                    Oct 30, 2025 
                  
              
              
            
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Cherry-picked from #57012